Method and apparatus for discovering devices in a network

ABSTRACT

In one embodiment, a method includes identifying whether there is a first device in a network that is expected to be associated with a discovery protocol but does not have the discovery protocol turned on. The method also includes providing a notification to a management arrangement when the first device is identified. The management arrangement manages the network, and the notification indicates that the first device is expected to be associated with the discovery protocol but does not have the discovery protocol turned on.

BACKGROUND

The present invention relates generally to networking.

Network discovery generally allows a device, e.g., a network elementsuch as a computer that is part of a network, to effectively detectother devices on the network. In other words, network discovery allows adevice within a network to essentially discover the topology of thenetwork. Network discovery is often a challenging task, particularly inrelatively large networks in which there are many devices.

Network discovery may be implemented using a variety of differentmethods. Such methods, however, have drawbacks. For example, although a“ping sweep” method is generally capable of discovering substantiallyall devices in a network by testing substantially every Internetprotocol (IP) address within a range, such testing generally consumes asignificant number of resources and, thus, places a significant load onthe network. Hence, a ping sweep method is not frequently implemented,resulting in some new devices within a network not being discoveredsubstantially in real-time.

A layer 2 discovery protocol allows a device to advertise its identityand capabilities on a network and to detect and store the identity andcapabilities of neighboring devices on the local network. The Link LayerDiscovery Protocol (LLDP) is a vendor-neutral Layer 2 protocol thatallows the previously described functions. The protocol was formallyratified as IEEE standard 802.1AB-2005 in May 2005. In general, LLDPallows each device to advertise information about itself to neighboringdevices in the network, and stores information it discovers from theneighboring devices. LLDP-based discovery is generally effective inallowing devices within a network to be discovered, provided that thedevices have LLDP turned “on” or otherwise deployed. However, not alldevices in a network have LLDP turned on. For example, older devices maynot support LLDP. As such, LLDP-based discovery may be unable todiscover substantially all devices within a network.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings in which:

FIG. 1 is a diagrammatic representation of a network that includes CiscoDiscovery Protocol (CDP) based devices in accordance with an embodiment.

FIG. 2 is a process flow diagram which illustrates one general method ofdiscovering devices in a network in accordance with an embodiment.

FIG. 3 is a process flow diagram which illustrates one method ofdetermining whether there is a network device within a propagationnetwork that is expected to be CDP-enabled but does not have CDP turnedon, e.g., step 213 of FIG. 2, in accordance with an embodiment.

FIG. 4 is a process flow diagram which illustrates a method ofprocessing a notification which indicates that an NMS is to attempt toturn on CDP for a remote network device that is expected to beCDP-enabled in accordance with an embodiment.

FIG. 5 is a diagrammatic representation of a CDP-enabled device inaccordance with an embodiment.

DESCRIPTION OF EXAMPLE EMBODIMENTS General Overview

According to one aspect of the present disclosure, a method includesidentifying whether there is a first device in a network that isexpected to be associated with a discovery protocol but does not havethe discovery protocol turned on. The method also includes providing anotification to a management arrangement when the first device isidentified. The management arrangement manages the network, and thenotification indicates that the first device is expected to beassociated with the discovery protocol but does not have the discoveryprotocol turned on.

DESCRIPTION

One layer 2 discovery protocol is Cisco Discovery Protocol (CDP). CDP isused to allow a network device to advertise its identity andcapabilities on a network. CDP is generally used by a network device toobtain the identity and capabilities of neighboring devices in anetwork. Network devices typically use CDP to periodically advertiseinformation to a multicast address on a network, substantially makingthe information available to any device or application on a local areanetwork (LAN). CDP may also be used by a network device to provideinformation about its interface, e.g., about the capabilities of apoint-to-point or multipoint interface.

When a device in a network is either unable to support LLDP or CDP, orotherwise does not have LLDP or CDP capability turned “on,” LLDP-basedor CDP-based discovery may be arranged to provide identify that deviceas being within the network. In other words, an indication may beprovided to a network management system (NMS), as for example by anetwork device, that there is a neighboring device in a network whichshould have LLDP or CDP turned on but does not. Using such anindication, the NMS, which is arranged to represent a map of a networktopology, may attempt to effectively turn on LLDP or CDP on theneighboring device. It should be appreciated that having LLDP or CDPcapability turned on includes, but is not limited to including,activating LLDP or CDP, and/or otherwise permitting LLDP-based orCDP-based discovery to discover the neighboring device.

In one embodiment, an indication that may be provided by a networkdevice to a NMS when a neighboring device which is expected to have LLDPor CDP turned on but does not may be a simple network managementprotocol (SNMP) notification. Such an SNMP notification may include, butis not limited to including, an address for the device that is sendingthe SNMP notification, information which identifies an interfacesupported by the neighboring device, and an address for the neighboringdevice which is expected to have LLDP or CDP turned on but does not. TheSNMP notification may effectively indicate to the NMS that a device at aremote end of a link is expected to have LLDP or CDP turned on but doesnot have LLDP or CDP turned on.

A network device, e.g., a local network router, that is CDP-enabled orCDP-capable and has CDP effectively turned on may poll its neighboringdevices to identify those neighboring devices. It should be appreciatedthat although a CDP-enabled device is described, a network device mayinstead be an LLDP-enabled device or a device that is enabled to supportany suitable layer 2 discovery protocol. That is, the present disclosureis not limited to being suitable for implementation with respect to CDPand LLDP, and may generally be applicable with respect to any suitablelayer 2 discovery protocol. In polling neighboring devices, a localnetwork router may determine if a neighboring device is CDP-enabled orif the neighboring device is expected to be CDP-enabled but does nothave CDP turned on.

The local network router may provide a NMS or other network managementdevice with information which indicates that a new device has beendiscovered within the network. Such a notification may indicate whethera particular neighboring device that was effectively discovered does nothave CDP turned on. In general, a new CDP-enabled device may be on anyinterface, as for example a point-to-multipoint interface. As will beappreciated by those skilled in the art, a device that is on apoint-to-multipoint interface is typically only known to the localnetwork router if the device is CDP-enabled.

Referring initially to FIG. 1, a network that includes CDP-enableddevices will be described in accordance with an embodiment. A network100 generally includes a plurality of devices such as devices 104, 108,112. Devices 104, 108, 112 may generally be any devices or nodes whichare capable of being networked. In one embodiment, device 104 may be arouter.

Devices 104, 108 are CDP-enabled and have CDP turned on, while device112 is expected, as for example by device 104, to be CDP-enabled, butdoes not have CDP turned on. Device 104 may generally send identifyingmessages to a multicast address on each active CDP-enabled interface,and monitors messages sent by other devices, e.g., device 108 which isCDP-enabled and has CDP turned on. It should be appreciated that whiledevice 104 may generally communicate with devices that are notCDP-enabled but are within a propagation network associated with device104. As will be understood by those skilled in the art, a propagationnetwork essentially defines boundaries, e.g., boundaries within anoverall network, relating to the discovery of devices. In other words, apropagation network substantially establishes boundaries within whichdevices are to be discovered.

Device 104 communicates with an NMS or a network management application116 to provide NMS 116 with information regarding devices known todevice 104. In the embodiment as shown, as device 108 is known to device104 and has CDP turned on, device 104 provides information to NMS 116regarding device 108. Such information may be provided usingsubstantially any method including, but not limited to, using a pollingmechanism associated with NMS 116. Such information may also be providedto device 104 through a notification. Upon obtaining the information,device 104 may populate a map.

Device 104 has at least one interface 120 a, 120 b that allows device104 to interface with other devices. As shown, interface 120 a is upsuch that device 104 may interface, e.g., communicate, with device 108,and interface 120 b is also up. Identification logic 124 is suitable foridentifying remote device 112 as being within a propagation networkassociated with device 104 and expected to be CDP-enabled, and as nothaving CDP turned on. In one embodiment, when a subnet mask is /30,identification logic 124 may also be arranged to identify the address,e.g., an Internet protocol (IP) addresses, for remote device 112. Itshould be appreciated that an IP address for remote device 112 may bewithin a range of IP addresses associated with, or otherwise expected tobe associated with, network 100.

With reference to FIG. 2, a method of discovering devices in a networkwill be described in accordance with an embodiment. A method 201 ofdiscovering devices in a network begins at step 205 in which a localnetwork device polls neighboring network devices within a propagationnetwork. The propagation network includes network devices which areconnected substantially directly to LANs. The polling is generallyperformed to gather information associated with the neighboring networkdevices, and is substantially propagated to the boundaries of thepropagation network. Polling neighboring network devices may includesending requests to, or otherwise soliciting announcements from, theneighboring network devices, as will be appreciated by those skilled inthe art. In one embodiment, where an interface is a point-to-pointinterface with a /30 subnet mask for an IP address, the local networkdevice has have a particular address, e.g., an IP address, that may besubstantially deduced.

After the local network device polls neighboring network devices withinthe propagation network, a determination is made in step 213 as towhether there is at least one neighboring network device that isexpected by the local network device to be CDP-enabled but does not haveCDP turned on. Such a determination will be discussed in more detailwith respect to FIG. 3. If the determination is that there is not atleast one neighboring network device that is expected by the localnetwork device to be CDP-enabled but does not have CDP turned on, theindication is that CDP is turned on for all network devices which werepolled. It should be appreciated that the indication may besubstantially inherent, and may not actually be provided to the localnetwork device. As such, process flow moves from step 213 to step 217 inwhich the local network device provides information to the NMS thatrelates to the CDP-enabled devices with CDP turned on. That is, the NMSis provided with information that may allow the NMS to updateinformation relating to network topology.

After information is provided to the NMS, a determination is made instep 221 as to whether the polling of neighboring network devices withinthe propagation network is to be repeated. It should be appreciated thatwhile polling of neighboring network devices may occur after informationis provided to the NMS, there is no dependency In one embodiment,polling may be repeated periodically, as for example at predeterminedtime intervals. Hence, a determination of whether to repeat polling maydepend upon, but is not limited to depending up, whether a predeterminedtime period has elapsed. In one embodiment, in lieu of repeatingpolling, once CDP is enabled on a neighboring device, the neighboringdevice may then poll its neighbors.

If it is determined in step 221 that polling is to be repeated, theprocess flow returns to step 205 in which the local network device pollsneighboring network devices within the propagation network.Alternatively, if it is determined that polling is not to be repeated,then the method of discovering devices in a network is completed.

Returning to step 213, if it is determined that there is at least oneneighboring device that is generally expected to be CDP-enabled but doesnot have CDP turned on, then

the local network device provides a notification to the NMS in step 229which indicates that the NMS is to attempt to turn on CDP for theneighboring network device that is expected by the local network deviceto be CDP-enabled but does not have CDP turned on. After thenotification is provided to the NMS, process flow moves to step 221 inwhich it is determined whether the polling is to be repeated.

FIG. 3 is a process flow diagram which illustrates one method ofdetermining whether there is a network device within a propagationnetwork that is expected to be CDP-enabled but does not have CDP turnedon, e.g., step 213 of FIG. 2, in accordance with an embodiment. Aprocess 213 of determining whether there is a neighboring device thatdoes not have CDP turned on begins at step 305 in which a local networkidentifies interfaces on the network device that are up. Once interfacesthat are up are identified, then it is determined in step 309 whetherthere is an interface that is up, e.g., active or connected, for whichthere appears to be no CDP neighbor, e.g., where there may be aCDP-enabled device for which CDP is not on. When an interface is up, butthere does not appear to be a neighbor with CDP turned on, thenimplication may be that there is a neighbor that is CDP-enabled but doesnot have CDP turned on. In one embodiment, the determination may includeascertaining whether there is an interface that is up or otherwiseactive, and appears to be substantially connected to a device that doesnot have CDP turned on.

If it is determined in step 309 that there is no interface that is upfor which there does not appear to be a CDP neighbor, an indication ismade in step 313 that there is effectively no neighboring device that isexpected to be CDP-enabled but does not have CDP turned on. After theindication is made, the process of determining whether there is aneighboring device that does not have CDP turned on is completed.

Alternatively, if it is determined in step 309 that there is aninterface that is up for which there appears to be no CDP neighbor, adetermination is made in step 315 as to whether there is a device todiscover within the propagation network, If it is determined that thereis no device to discover within the propagation network, process flowproceeds to step 313 in which a local indication is made that there iseffectively no neighboring device that is expected to be CDP-enabled butdoes not have CDP turned on. If, however, it is determined that there isa device to discover within the propagation network, then an indicationis made in step 317 that there is a neighboring network device, e.g., adevice that is a neighbor to the local network device within thepropagation network, that is expected to be CDP-enabled, but does nothave CDP turned on. In one embodiment, if the local network devicedetermines that there is an interface that is up, but no apparent CDPneighbor, the local network device may send an SNMP notification to theNMS in which it is effectively expressed that CDP or, more generally,LLDP, should be turned on for that neighbor. The process of determiningwhether there is a neighboring device that does not have CDP turned onis completed after the indication is made in step 317.

A local network device typically alerts an NMS or a network managementapplication when the local network device has essentially identified aneighboring network device that is expected to be CDP-enabled but doesnot have CDP turned on. Upon being alerted or otherwise notified, theNMS may effectively process the information provided with the alert ornotification. During processing, the NMS may identify whether theneighboring network device identified in the alert or notification iseither CDP-enabled and not turned on, or if the neighboring networkdevice is not CDP-enabled. FIG. 4 is a process flow diagram whichillustrates a method of processing a notification which indicates thatan NMS is to attempt to turn on CDP for a remote network device that isexpected to be CDP-enabled in accordance with an embodiment. A method401 of processing a notification begins at step 405 in which an NMSreceives a notification from a local network device regarding a remoteneighboring network device. It should be appreciated that while an NMSis described, a network management application or substantially anyapplication with network management capabilities may instead receivenotification regarding a remote neighboring network device.

Once the NMS receives or otherwise obtains a notification regarding aremote neighboring network device, the NMS identifies informationcontained in the notification in step 409. The information contained inthe notification includes, but is not limited to including, an interfacetype and an indication of an address, e.g., an IP address, for theremote neighboring network device. As will be appreciated by thoseskilled in the art, a seed router may pool appropriate addressresolution protocol (ARP) tables to discover the IP address if theremote neighboring device before the IP address is provided to the NMS.In one embodiment, the interface type may be a point-to-point interfacetype or a point-to-multipoint device, e.g., a multi-point device. Whenan interface is a point-to-point interface, a local network device isaware of whether there is a remote, CDP-capable neighboring device. Whenan interface is a multipoint interface, a local network device generallyis unable to determine how many CDP-capable devices are available on thenetwork.

A determination is made in step 413 as to whether a remote IP addresscontained interface type included in the notification is a real IPaddress. The remote IP address may be, for example, associated with apoint-to-point link with a /30 subnet.

If it is determined in step 413 that the remote IP address contained inthe notification is a real IP address, then in step 417, CDP is turnedon for the remote neighboring device. The NMS may cause CDP to be turnedon for the remote neighboring device using any suitable method. AfterCDP is turned on for the remote neighboring device, the method ofprocessing a notification is completed.

Alternatively, if it is determined in step 413 that the remote IPaddress contained in the notification is not real, the indication, inone embodiment, is that the remote IP address is unknown, e.g., 0.0.0.0.When the remote IP address is unknown, the implication may be, forexample, that there is a point-to-point interface type with no /30subnet or that there is a point-to-multipoint interface type.

If the remote IP address contained in the notification is determined notto be real in step 413, then process flow moves to step 445 in which theNMS investigates to discover whether one or multiple devices that areeffectively connected to the local device should have CDP turned on. Anysuitable method may be used to discover whether one or multiple devicesshould have CDP turned on. In step 451, the NMS discovers an IP addressfor a remote device, or IP addresses for remote devices, that aresubstantially connected to the local device that should have CDP turnedon. After the NMS discovers one or more IP addresses, the NMS turns onCDP in step 453 for the one for the one or more remote devices thatcorrespond to the one or more IP addresses. Once the one or more remotedevices are turned on, the

the method of processing a notification is completed.

As mentioned above, a CDP-enabled device that is a local network deviceis generally configured to notify an NMS or network managementapplication that there may be a remote neighboring device that isCDP-enabled but does not have CDP turned on. With reference to FIG. 5,one CDP-enabled device that is a local network device will be describedin accordance with an embodiment. A CDP-enabled device 504, which may bea router, includes a processing arrangement 540 that is arranged toperform functions associated with CDP-enabled device 504. By way ofexample, if device 504 is a router, processing arrangement 540 mayinclude routing functionality 554 that is configured to allow device 504to receive and to route signals. In general, processing arrangement 540may include at least one microprocessor.

Device 504 also includes a communications arrangement 536 that isarranged to cooperate with processing arrangement 540 to allow device504 to receive communications from, and provide communications to, otherdevices and/or a NMS in the same network as device 504. Communicationsarrangement 536 generally includes at least one interface 520 that isconfigured to allow device 504 to communicate with, as for example toexchange information with, devices which are within the same network asdevice 504. If interface 520 is up, the indication is that device 504 iseffectively connected to another device through interface 520.Alternatively, if device 520 is down, the indication is that device 504is effectively not connected to any other device through interface 520.

Identification arrangement 524 is configured to allow addresses ofdevices which are neighbors to device 504 to be identified. For example,identification arrangement 524 may identify an address associated with aneighboring device that is substantially connected to, or otherwise incommunication with, device 504 through interface 520. Interface 520 maygenerally allow device 504 to communicate with other devices or entitieson a network.

A notification arrangement 558 may be included in identificationarrangement 524. Notification arrangement 558 is generally configured tosend or otherwise provide an alert or a notification to an NMS whenidentification arrangement 524 identifies a neighboring device that isexpected to be CDP-enabled but does not have CDP turned on. Notificationarrangement 558 may create a notification, as for example an SNMPnotification, which includes, but is not limited to including, anaddress of device 504, information regarding interface 520 such as aninterface type, and an address of the neighboring device that isexpected to be CDP-enabled but does not have CDP turned on. Aspreviously mentioned, the interface type may be a point-to-pointinterface type or a point-to-multipoint interface type. A point-to-pointinterface type may have a /30 subnet, or may be substantially without a/30 subnet. In one embodiment, the address of the neighboring device maybe an IP address.

A memory 532 allows information obtained by device 504 to be stored.Memory 532 may generally store information which is utilized byidentification arrangement 524 including, but not limited to including,a range of addresses associated with a network of which device 504 is apart. Memory 532 may be embodied as a database, random-access memory,read-only memory, and/or any other suitable data structure that isarranged to store data or information.

Although only a few embodiments of the present disclosure have beendescribed, it should be understood that the present disclosure may beembodied in many other specific forms without departing from the spiritor the scope of the present disclosure. By way of example, a localnetwork device has been described as notifying a NMS or similarapplication when it is determined that a remote neighboring networkdevice does not have CDP turned on, but is expected to have CDP turnedon. A local network device may, in some instances, determine whether anaddress, e.g., an IP address, associated with the remote neighboringnetwork device is within a range of addresses. If the address is withinthe range of addresses, the local network device may notify the NMS thatthe remote neighboring network device is expected to have CDP turned on.If, however, the address is not within the range of addresses, the localnetwork device may identify the remote neighboring network device as notbelonging to the same network as the local network device. When thelocal network device identifies the remote neighboring network device asnot belonging to the same network as the local network device, the localnetwork device may decide not to send a notification regarding theremote neighboring network device to the NMS.

In one embodiment, a NMS configures a propagation network in a selecteddevice, e.g., router, within an overall network. Such a propagationnetwork may be arranged to contain a network and/or subnet of one ormore networks to be discovered. The propagation network may bepropagated, as for example through a CDP type-length-value (TLV) frameformat, to substantially all interfaces to which the network to bediscovered belongs.

While notification which indicates that there may be a CDP-enableddevice on which CDP is not turned on is described as being sent to anNMS, it should be appreciated that notification which indicates thatthere may be an LLDP-enabled device on which LLDP is not turned on mayalso be sent to an NMS or similar device without departing from thespirit or the scope of the present disclosure. For an embodiment inwhich LLDP-based discovery is supported, notification may be associatedwith an SNMP notification contained in an LLDP-EXT-MED-MIB.

In general, CDP and LLDP, as well as any other suitable discovermechanism, may run or execute on any suitable network device. Suchdevices include, but are not limited to including, computers, routers,bridges, access servers, phones, and switches.

Once the disposition of a remote network device which is expected to beCDP-enabled but does not have CDP turned on is determined, an NMS mayeffectively decide what actions to take, if any, in relation to theremote network device. For instance, if a remote network device isdetermined not to be CDP-enabled, the NMS may decide how to include thatremote network device in its rendering of a network topology.

The embodiments may be implemented as hardware and/or software logicembodied in a tangible medium that, when executed, is operable toperform the various methods and processes described above. That is, thelogic may be embodied as physical arrangements or components. Forexample, an arrangement that effectively deduces whether there is a CDPneighbor may include hardware logic, software logic, or a combination ofboth hardware and software logic. The tangible medium may besubstantially any computer-readable medium that is capable of storinglogic which may be executed, e.g., by a computing system, to performmethods and functions associated with the embodiments.

The steps associated with the methods of the embodiments may varywidely. Steps may be added, removed, altered, combined, and reorderedwithout departing from the spirit of the scope of the presentdisclosure. Therefore, the present examples are to be considered asillustrative and not restrictive, and the disclosure is not to belimited to the details given herein, but may be modified within thescope of the appended claims.

1. A method comprising: identifying whether there is a first device in anetwork that is expected to be associated with a discovery protocol butdoes not have the discovery protocol turned on; and providing anotification to a management arrangement when the first device isidentified, the management arrangement being arranged to manage thenetwork, wherein the notification is arranged to indicate that the firstdevice is expected to be associated with the discovery protocol but doesnot have the discovery protocol turned on.
 2. The method of claim 1wherein the discovery protocol is one selected from the group includinga Cisco Discovery Protocol (CDP) and a Link Layer Discovery Protocol(LLDP).
 3. The method of claim 2 wherein the management application is aNetwork Management Server (NMS).
 4. The method of claim 2 whereinidentifying whether there is a first device in the network includesutilizing a second device in the network to identify whether there isthe first device in the network.
 5. The method of claim 4 whereinutilizing the second device in the network to identify whether there isa first device in the network includes determining whether there is afirst interface associated with the second device that is active and isarranged to be in communication with the first device.
 6. The method ofclaim 5 wherein the notification includes an indication of an addressassociated with the first device and an indication of an interface typeassociated with the first interface.
 7. The method of claim 6 whereinthe interface type is one selected from the group including apoint-to-point interface type and a point-to-multipoint interface type.8. The method of claim 6 wherein the notification is a Simple NetworkManagement Protocol (SNMP) notification.
 9. The method of claim 1wherein the network is a propagation network, the method furtherincluding: defining boundaries associated with the propagation network,wherein identifying whether there is a first device in the network thatis expected to be associated with the discovery protocol but does nothave the discover protocol turned on includes discovering the firstdevice within the boundaries associated with the propagation network.10. The method of claim 1 further including: discovering new devices inthe network, wherein discovering the new devices in the network includesidentifying whether there is the first device in the network that isexpected to be associated with the discovery protocol but does not havethe discovery protocol turned on.
 11. Logic encoded in one or moretangible media for execution and when executed operable to: identifywhether there is a first device in a network that is expected to beassociated with a discovery protocol but does not have the discoveryprotocol turned on; and provide a notification to a managementarrangement when the first device is identified, the managementarrangement being arranged to manage the network, wherein thenotification is arranged to indicate that the first device is expectedto be associated with the discovery protocol but does not have thediscovery protocol turned on.
 12. The logic of claim 11 wherein thediscovery protocol is one selected from the group including a CiscoDiscovery Protocol (CDP) and a Link Layer Discovery Protocol (LLDP). 13.The logic of claim 12 wherein the management application is a NetworkManagement Server (NMS).
 14. The logic of claim 12 wherein the logicoperable to identify whether there is a first device in the network isfurther operable to utilize a second device in the network to identifywhether there is the first device in the network.
 15. The logic of claim14 wherein the logic operable to identify whether there is a firstdevice in the network using the second device in the network is furtheroperable to determine whether there is a first interface associated withthe second device that is active and is arranged to be in communicationwith the first device.
 16. The logic of claim 15 wherein thenotification includes an indication of an address associated with thefirst device and an indication of an interface type associated with thefirst interface.
 17. The logic of claim 16 wherein the interface type isone selected from the group including a point-to-point interface typeand a point-to-multipoint interface type.
 18. The logic of claim 16wherein the notification is a Simple Network Management Protocol (SNMP)notification.
 19. The logic of claim 10 wherein the network is apropagation network, the logic further being operable to: defineboundaries associated with the propagation network, wherein the logicoperable to identify whether there is a first device in the network thatis expected to be associated with the discovery protocol but does nothave the discover protocol turned on is further operable to discover thefirst device within the boundaries associated with the propagationnetwork.
 20. The logic of claim 10 further operable to: discover newdevices in the network, wherein the logic operable to discover the newdevices in the network includes the logic operable to identify whetherthere is the first device in the network that is expected to beassociated with the discovery protocol but does not have the discoveryprotocol turned on.
 21. An apparatus comprising: means for identifyingwhether there is a first device in a network that is expected to beassociated with a discovery protocol but does not have the discoveryprotocol turned on; and means for providing a notification to amanagement arrangement when the first device is identified, themanagement arrangement being arranged to manage the network, wherein thenotification is arranged to indicate that the first device is expectedto be associated with the discovery protocol but does not have thediscovery protocol turned on.
 22. An apparatus comprising: a processingarrangement; at least one interface, the interface being configured toallow the apparatus to communicate on a network when the interface isactive; and an identification arrangement, the identificationarrangement being configured to determine when the interface is activeand, when the interface is active, to determine if the interface is incommunication with a device that is expected to be associated with adiscovery protocol but does not have the discovery protocol turned on,wherein the identification arrangement is further configured to providea notification that the device that is expected to be associated with adiscovery protocol does not have the discovery protocol turned on if theinterface is in communication with the device that is expected to beassociated with the discovery protocol but does not have the discoveryprotocol turned on.
 23. The apparatus of claim 22 wherein the discoveryprotocol is one selected from the group including a Cisco DiscoveryProtocol (CDP) and a Link Layer Discovery Protocol (LLDP).
 24. Theapparatus of claim 23 wherein the identification arrangement isconfigured to provide the notification to a Network Management Server(NMS) associated with the network.